Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for providing additional kwargs for sqlalchemy connection #290

Merged
merged 3 commits into from
Nov 11, 2023

Conversation

amaralvieira
Copy link
Contributor

Additional keyword arguments may vary across dialects, and some connections may not work without specific keyword arguments.

Additional keyword arguments can now be added at the same level as the connection_url.

Example:

default:
  outputs:
    dev:
      type: duckdb
      path: /tmp/dbt.duckdb
      plugins:
        - module: gsheet
          config:
            method: oauth
        - module: sqlalchemy
          alias: myoracledb
          config:
            connection_url: "{{ env_var('DBT_ENV_SECRET_SQLALCHEMY_URI') }}"
            thick_mode: true
        - module: path.to.custom_udf_module

Additional keyword arguments may vary across dialects, and some connections may not work without specific keyword arguments.

Additional keyword arguments are to be added at the same level as connection_url.

Example:
```
default:
  outputs:
    dev:
      type: duckdb
      path: /tmp/dbt.duckdb
      plugins:
        - module: gsheet
          config:
            method: oauth
        - module: sqlalchemy
          alias: sql
          config:
            connection_url: "{{ env_var('DBT_ENV_SECRET_SQLALCHEMY_URI') }}"
            thick_mode: true
        - module: path.to.custom_udf_module
```
@jwills
Copy link
Collaborator

jwills commented Nov 10, 2023

Ah, this is great— thank you!

@jwills jwills merged commit 1cbda93 into duckdb:master Nov 11, 2023
29 of 30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants